home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
tf21.zip
/
TF-SYSOP.DOC
< prev
next >
Wrap
Text File
|
1991-01-16
|
15KB
|
314 lines
================= ===========
/ /
/ /
/ _____ _____ /______ _____ ____ ____ ____
/ / / / / / / / / / / / /
/ /____/ /____ /___/ / / / /___/ / /__
/ / / / /\ / / / /\ / /
_/ _/ _/ ______/ _/ \_ _/ /____/ _/ \_ /____ /____
A DOOR GAME DESIGNED TO RUN WITH PCBOARD 14.x
Version 2.1
Copyright (c) 1991
by
Cam N. DeBuck
=====================[ Task Force SysOp Instructions ]=======================
NOTES: You MUST have SHARE loaded even on a single node BBS!!!
: This version of TaskForce will not run at 38400. You will
: need to get something like PORTER until the C version of
: TaskForce is complete (Which will support up to 115200 Baud).
Task Force is an interactive multi-player space war/trade simulation that was
written specifically to be run as a BBS 'door' on PCBOARD 14.x.
Task Force 2.1 no longer supports ANY version of PCBOARD prior to 14.x
System requirements are:
MS/PC DOS 3.0 or higher.
256K memory (per partition if multi-tasking).
PCBOARD 14.x
500K Hard Drive Space.
Setting up Task Force on your PCBOARD is a simple process, if you follow
these step by step instructions.
1. Create a sub-directory for the game. You may call it whatever you
wish. This is where all Task Force activity will take place. We will
now refer to this as the <Task Force Sub-directory>.
2. Copy all files from the master Archive (TF21.ZIP) into the
<Task Force Sub-directory>. You should now have the following files
in the <Task Force Sub-directory>:
TF-SYSOP.DOC : Documentation for the SysOp
TASKFORC.DOC : Player documentation for the game
TASKFORC.EXE : The main door game program
NEXTDAY.EXE : Once-a-day game update utility
TF-INIT.EXE : Initializes a new game
TASKEDIT.EXE : Minimal game re-configuration utility
TFVER2.COD : Registration 'COD' file
TF-1.BAT : Sample Batch file for BBS Node #1
TF-2.BAT : Sample Batch file for BBS Node #2
NOTE: This release of the game requires the presence of BRUN30.EXE on
your DOS path or in the door game directory. Be sure to use the version
of BRUN30.EXE which has been 'DTR patched' so it will not drop carrier
as soon as someone opens the door game.
3. Change to the <Task Force Sub-directory> and run the program TF-INIT.
This program "sets up" the universe or playing field. It must be run
or else Task Force will not run. If you ever want to re-start the
game (destroying all current players etc...), then run TF-INIT again.
4. Task Force initially gives each player 50 Turns and 30 Minutes each
day. It also keeps dead players from playing the game for 1 day. This
can, however, be changed. If you wish to change these values, run the
quick edit program, TASKEDIT. It will ask you about the number of
turns, time, days dead, and several other game parameters. This can
be run at anytime during a game, but existing players' values will
not change until NEXTDAY is run.
For a more comprehensive editor, you should get a copy of TF-EDIT.ZIP.
This version if for REGISTERED users only and contains a more COMPLETE
Editor for doing just about everything you ever wanted. If you have
the registered version of 2.1, then it will be on Registered Disk.
(Available from one of the BBS's in the TASKFORC.DOC)
5. Now batch files must be set-up for all nodes that will access Task
Force. Set PCBOARD up to access the Task Force batch file you will
now create (See PCBOARD documentation). After this has been done,
you will need to create the batch file that PCBOARD has to access
when the Task Force door is opened. It should look something like:
@ECHO OFF
CLS
CD <Task Force Sub-directory>
TASKFORC <Location Of PCBOARD.SYS> </19200> </SLAVE>
CD <PCBOARD Sub-directory>
BOARD (batch file to run that node)
NOTE: The com port number is taken from the PCBOARD.SYS file.
<Location Of PCBOARD.SYS> is a MANDATORY command line parameter that
defines the path name and filename of PCBOARD.SYS
</19200> is an optional command line parameter that is needed only if
you are locking your com port at 19.2K baud.
</SLAVE> is an optional command line parameter that is needed only if
you are trying to run the game on a 'Slave Card'.
<PCBOARD Sub-directory> = 'main' PCBOARD BBS Sub-directory
Here are two sample batch files:
NODE #1 NODE #2
---------------------------- -----------------------------
@ECHO OFF @ECHO OFF
CLS CLS
C: C:
CD\DOORS\TASKFORC CD\DOORS\TASKFORC
TASKFORC C:\PCB\PCBOARD.SYS TASKFORC C:\PCB2\PCBOARD.SYS
CD\PCB CD\PCB2
BOARD BOARD2
If you are running more than one node (which many of you are), each
node will obviously need its own batch file. However, they should all
call the same Task Force game in the same sub-directory.
6. As with all previous versions of Task Force, you MUST have the DOS
program called 'SHARE' loaded before the game will run. This is the DOS
utility required for 'networking'. You will find it on your DOS master
disk, or subdirectory. SHARE affects nothing else, so the best place
to load it is in the autoexec.bat. Due to several requests, we are looking
at the possibility of letting the sysop have the option of whether or not
to use SHARE in a future release (for NON-network systems).
NOTE: You MUST have SHARE loaded even on a single node BBS!!!
7. WATCHDOG, or equivalent programs that check for a carrier drop must NOT
be active at the same time Task Force is running. Either turn them
off, or do not run them at all. The game fully traps all errors and
carrier drops, so your board will be safe.
8. NEXTDAY now needs to be added to your EVENT. NEXTDAY needs to be run
in the <Task Force Sub-directory>. For more information on creating
an EVENT, see PCBOARD documentation. Your EVENT.SYS batch file needs
to include code something like this:
C:
CD <Task Force Sub-directory>
NEXTDAY <filename1> <filename2>
The above batch file should be inserted into your current EVENT.SYS
batch file. If you do not currently have an EVENT, see the PCBOARD
documentation to help you make one.
<filename1> is an optional parameter. If it is not included, it will in
no way affect how the game works. However, if included, all players in
the game will be ranked put in order from high to low. The file will be
in standard ASCII so it can be made into a bulletin or news so
everybody can see how the game is going. Everybody is ranked (not just
the top ten). Here is an example of how to do this:
NEXTDAY c:\pcb\gen\blt1
This would put the player rankings in BLT1. The path might need to be
modified for your system.
<filename2> is another optional parameter. Obviously, you can NOT use a
filename here unless you have also specified a <filename1>. If this
second filename is not included, it will in no way affect how the game
works. However, if included, all DEAD players in the game will be listed
in a 'Cemetary Report' which is also in standard ASCII so it can be made
into a bulletin or news so everybody can see who is dead and for how many
days they are locked out of the game before they can play again.
An example of this is as follows:
NEXTDAY c:\pcb\gen\blt1 c:\pcb\gen\blt2
This would put the player rankings in BLT1 and the cemetary report in
BLT2. The path might need to be modified for your system.
The purpose of NEXTDAY is to provide players with production,
subtract food, water, and raw material usage, and do other clean up
work on the universe. Every time this is run, their turns and time are
reset.
9. TASKFORC.DOC is the player documentation, and must be read by all
players if the game is to be successful. Do anything you can to make
it highly accessible. Make it available for anybody to download as
well as perhaps putting it in a bulletin.
10. If you wish to have two or more totally independent games going at one
time, just make another sub-directory and do all steps over for that
subdirectory. The game will handle up to 400 people, and the more
people per game, the funner it is, so unless you have an extremely
large game, or a demand for more than one game in progress, it is
suggested that you only have one.
11. When you first log-on to the game, the system name and name of the
sysop are displayed. If there are any misspellings or you wish to
have it worded slightly differently, leave a message on the home BBS.
The C version of TaskForce will have an EDITOR to edit any of the lines
which will provide Sysops with a version they like for wording.
12. The $25 you paid for the program includes a lifetime subscription to
The Professional Executive Connection and the special 'support'
conference. Any new updates which are made will always be posted for
download in this conference. Please be sure to spell the name of your
BBS exactly like you want it displayed within the door game and also the
name of the SysOp.
BETA are always availble in the Support Conference and are availble
only to REGISTERED users. A new COD file is availble during BETA
testing.
13. If you have any troubles, suggestions or questions, feel free to call
and leave a message to the SysOp.
14. Voice support is available by calling: (801)489-7558 7p.m. - 11 p.m MST
Have Fun Playing Task Force!
----[ Program History ]------------------------------------------------------
0 to 1.21 (whenever) - These early versions were all written/sold/released by
Jeff Petersen. He kept NO records of who purchased what version and can not
even find a copy of his source code any more. Unfortunately, this means that
there is no other 'historical' data on those early versions.
Updates by Carl VERVAN SoftWare
--------------------------------
1.22V - (Fall 1987) - This was my first involvement with the program. I was
encountering some rather severe bugs while trying to run the door on my BBS
and Jeff asked me to de-bug the 1.21 version. I eliminated most of the known
bugs and made some other minor modifications. The 'V' means 'beta' version.
1.22 - (05 JAN 1988) - This was the first 'formal' release of the program
after it was modified by VERVAN. Some more minor bugs were zapped and the
combat algorithm was completely redesigned. PCBOARD 12.1 support ONLY!
2.0 - (09 JAN 1989) - This is a major update.
* The original author gave VERVAN all rights to the program.
* The program was updated so it would run under PCBOARD 14.0 and all
support for previous versions of PCBOARD was dropped.
* The carrier drop problem was fixed. In the old 1.22 version, if a
caller dropped carrier during the game's news file scan, the system
would lock up. Please report any further problems of this nature ASAP!
* The author's "back door" was removed from the code. In ALL earlier
versions, anyone knowing the secret of the back door could literally
tell the game to self-destruct. I HATE 'back doors' and version 2.0
of the program does not have ANY 'back doors'.
* The NEXTDAY routine was completely rewritten. The process was speeded
up by at least a factor of 5 and a number of new functions were built
in. The old TFREPORT program was incorporated into the NEXTDAY routine
and the video screen display now tells the SysOp what is happening.
* The combat routine was tweaked one more time. The shield generators
were redesigned. A player who is sitting still and defending will be
able to apply more power to his shields and thus deflect more of the
enemy shots. On the other hand, a player who initiates an attack will
find that the power drain makes his shields slightly less effective.
* More miscellaneous bugs were fixed.
* There were also many other minor changes made to the game.
Cam N. DeBuck
-------------
2.1 (16 Jan 1991) - This is my first release of the program. Very few
changes were made in the source code. Rewrite of the program has started
in Turbo C and new features are being added.
----[ Licensing Agreement ]--------------------------------------------------
Task Force is copyrighted by Cam N. DeBuck and all rights are reserved. This
program is NOT 'public domain' or 'shareware'. Task Force is a COMMERCIAL
product. The nominal $25 fee that you pay makes it possible for us to provide
you with support and updates as well as future doors. Anyone who purchases this
program is granted a non-exclusive license to run this game on ONE bulletin
board system (BBS). While you are welcome to give the DEMO version to anyone,
the COD file is declared to be Cam N. DeBuck's proprietary property. As such,
you may NOT distribute your customized COD file to anyone. If anyone is
interested in previewing the program before purchasing it, a demonstration
copy is available.
Cam N. DeBuck, its principles and agents are not liable for any direct or
incidental damage caused by the use, misuse, or failure to use this program.
NOTE: The demo version will run in LOCAL AND COM1 AND COM2! The C version
of the program will run on com ports 1 - 8.
Thank you for your support. For more information or help contact:
Cam N. DeBuck
235 East 1300 North
Springville, Utah 84663
BBS Support: The Professional Executive Connection
(801) 489-3558 [HST 1440] Public
BBS Support: Hackers' Haven
(801) 224-7358 [HST 9600] Public
(801) 224-4031 [2400] Public
(801) 224-7961 [HST 1440] Registered Users
Both BBS's are operated by me, but are two totally different BBS's. You'll
probably find that The Professional Executive Connection is NOT BUSY compared
to the other BBS.
====[ END OF SYSOP DOCUMENTATION FOR TASK FORCE ]============================